home *** CD-ROM | disk | FTP | other *** search
- Path: uni-paderborn.de!magick
- From: magick@uni-paderborn.de (Mario Kemper)
- Newsgroups: comp.sys.amiga.networking
- Subject: Re: FlushLibs
- Date: 15 Feb 1996 09:31:56 GMT
- Organization: Universitaet Paderborn, Germany
- Message-ID: <4fuuic$a8n@news.uni-paderborn.de>
- References: <1013.6615T463T758@user1.channel1.com> <4fq53n$7p2@news.uni-paderborn.de> <1609.6618T450T2864@user1.channel1.com>
- NNTP-Posting-Host: condor.uni-paderborn.de
- X-Newsreader: TIN [version 1.2 PL2]
-
- : >As the OS flushes libs automatically in low memory situations, you normally
- : >only need it to see, if a program has memory leaks.
-
- : >Using is simple, just starting it. If i'm not wrong, it just allocates a huge
- : >amount of memory. If exec can't fulfill the request, it flushes all unused
- : >librarys from the system.
-
- : Thank you for your reply. I have another question. What is a memory leak?
-
- If a program allocates memory, but frees only a part of it, some amount
- of memory stays allocated. To see, if you free all memory, you do the
- following:
-
- avail flush total (Flushes everything, that is not used, and gives you
- the total amount of free memory)
-
- program (Start your program, play with it an then quit it)
-
- avail total flush (The same as above, there should be no difference in
- the output).
-
- The reason for the flush is, if a program opens a library, the library
- stays in memory, until its flushed.
-
- --
- Mario Kemper magick@bundy.lip.owl.de
- University of Paderborn (Germany). magick@uni-paderborn.de
-
-